Compile tests too but don't run them#52
Merged
Merged
Conversation
Collaborator
Author
|
|
Collaborator
Author
|
So does This looks to be produced by Also present in To start with, let's just check for a file of the form |
Collaborator
Author
|
Works for these two projects at least. After running: |
Collaborator
Author
|
A full run ( No more builds failed than prior to compiling tests, and a test jar was recovered for about 60% of projects: 😅 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #48.
The main idea of changing
-Dmaven.test.skip=trueto-DskipTestsgave successful compilation on an example project:But although that resulted in more bytecode feature metadata being generated, the output jar looks to be unchanged compared to an earlier run (
23):How to get the tests into the same jar? Do we even want this?
Maybe we should create a separate
.tests.jarfile. Doing this via Maven is probably tricky (requiring automated messing withpom.xml, and it would be different depending on which plugin(s) were used to build the existing jar) so it would be easier to build this ourselves after running Maven.